[Setup]


;
;      Name: HighPriority
;    Values: 0, 1 (default)
;   Summary: (optional)
;		ISAPI Filter priority.
; Behaviour:
;		If 1, the ISAPI filter runs with high priority. 
;		If 0, the ISAPI filter runs with low priority. 
;
HighPriority=1


;
;      Name: RulesFile
;    Values: filename (text)
;   Summary: (optional)
;		Default rules filename.
; Behaviour:
;		This is the default rules file to be used across all zones. Each 
;		zone can define its own ini file. It must not contain the path,
;		only the filename. Defaults to this same file.
;
RulesFile=Default.ini


;
;      Name: ZonesToExclude
;    Values: 0, 1 (default)
;   Summary: (optional)
;		IisShield can be configured to act upon every single request on Iis except
;		the ones belonging to specific zones. Or it can be confiured the other way around, 
;		i.e, its does not act on any request except the ones belonging to specific zones.
; Behaviour:
;		If 0, only requests that belong to the zones listed in section [ZonesToInclude] are filtered.
;		If 1, requests that belong to the zones listed in section [ZonesToExclude] are not filtered.
;
;ZonesToExclude=1


;
; See "ZonesToExclude" key
;
[ZonesToExclude]
SampleZone
SampleZone1

[ZonesToInclude]



;
;	Zones are used to specify which requests are included or excluded requests from 
;	the filtering engine. A zone is made of the optional items:
;		- target address <TargetAddr>
;		- target port <TargetPort>
;		- target url <TargetUrl>
;		- rules file <RulesFile>
;
;	A zone can also override the default rules file by specifying a rules file to be
;	applied to all requests part of the zone.
;
;	For a request t be considered part of a zone, the following steps are taken whenever
;	a request comes into Iis:
;		- if <TargetAddr> is defined, then the target address of the request must match <TargetAddr>
;		- if <TargetPort> is defined, then the target port of the request must match <TargetPort>
;		- if <TargetUrl> is defined, then the url of the request must start with <TargetUrl>
;
;	The zone that first matches a request is the chosen zone. Zones are checked
;	in the order they are defined in the configuration file. Zones that do not 
;	define <TargetAddr>, <TargetPort> and <TargetUrl> are ignored. 
;
;		[SampleZone]
;		TargetAddr=127.0.0.1
;		TargetPort=80
;		TargetUrl=/
;		RulesFile=sample.ini
;
;	See below for an explanation of the key usage:


;
;[SampleZone]
;
;
;
;      Name: TargetAddr
;    Values: text
;   Summary: (optional)
;		The target ip address of the http request
; Behaviour:
;		Requests with this target ip address are considered part of this zone.
;
;TargetAddr=1
;
;
;
;      Name: TargetPort
;    Values: numeric
;   Summary: (optional)
;		The target port number of the http request
; Behaviour:
;		Requests with this target port number are considered part of this zone.
;
;TargetPort=1
;
;
;
;      Name: TargetUrl
;    Values: url (text)
;   Summary: (optional)
;		The prefix url of the requests belonging to this zone.
;		Example: /folder/foo.aspx
; Behaviour:
;		Incoming requests whose url starts with 
;		<TargetUrl> are considered part of this zone.
;
;TargetUrl=/
;
;
;
;      Name: RulesFile
;    Values: filename (text)
;   Summary: (optional)
;		The rules file to apply to this zone.
; Behaviour:
;		Incoming requests part of this zone will be validated against this rules file.
;		Defaults to the default rules file defined in [Setup] section.
;
;RulesFile=sample.ini
;


[SampleZone]
TargetAddr=127.0.0.1
TargetPort=80
TargetUrl=/
RulesFile=sample.ini

[SampleZone1]
TargetAddr=127.0.0.1
TargetPort=80
TargetUrl=/
RulesFile=sample.ini